System, method, and product for selecting timing information based on subcarrier spacing

ABSTRACT

User equipment performs autonomous time adjustment that includes selecting a Timing Error Limit (i.e. T e_NR ) and Maximum Autonomous Time Adjustment Step (i.e. T q_NR ) based on bandwidth (BW) and subcarrier spacing (SCS). In one embodiment, given a certain downlink BW, if the SCS=x(kHz) and the T e_NR  of this SCS is N, then the T e_NR  of SCS=x/2(kHz) is 2*N. Given a certain downlink BW, if the SCS=x(kHz) and the T e_NR  of this SCS is N, then the T e_NR  of SCS=2*x(kHz) is N/2. For example, given BW=10 MHz, if the T e_NR  of SCS=30kHz is n*T s_NR  (T S_NR  is the basic timing unit for NR system), then the T e_NR  of SCS=60 kHz is N/2*T s_NR , and the T e_NR  of SCS=15 kHz is 2*N*T s_NR .

RELATED APPLICATION

This application claims the benefit under 35 U.S.C. § 119(e) of U.S.Provisional Application No. 62/476,420 filed Mar. 24, 2017, which ishereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

The present disclosure relates to cellular communications and morespecifically to selecting cellular timing configurations.

BACKGROUND

Wireless mobile communication technology uses various standards andprotocols to transmit data between a base station and a wireless mobiledevice. Wireless communication system standards and protocols caninclude the 3rd Generation Partnership Project (3GPP) long termevolution (LTE); the Institute of Electrical and Electronics Engineers(IEEE) 802.16 standard, which is commonly known to industry groups asworldwide interoperability for microwave access (WiMAX®); and the IEEE802.11 standard for wireless local area networks (WLAN), which iscommonly known to industry groups as Wi-Fi®. In 3GPP radio accessnetworks (RANs) in LTE systems, the base station can include a RAN Nodesuch as a Evolved Universal Terrestrial Radio Access Network (E-UTRAN)Node B (also commonly denoted as evolved Node B, enhanced Node B,eNodeB, or eNB) and/or Radio Network Controller (RNC) in an E-UTRAN,which communicate with a wireless communication device, known as userequipment (UE). In fifth generation (5G) wireless RANs, RAN Nodes caninclude a 5G Node, new radio (NR) node or g Node B (gNB).

RANs use a radio access technology (RAT) to communicate between the RANNode and UE. RANs can include global system for mobile communications(GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN),Universal Terrestrial Radio Access Network (UTRAN), and/or E-UTRAN,which provide access to communication services through a core network.Each of the RANs operates according to a specific 3GPP RAT. For example,the GERAN implements GSM and/or EDGE RAT, the UTRAN implements universalmobile telecommunication system (UMTS) RAT or other 3GPP RAT, and theE-UTRAN implements LTE RAT.

A core network can be connected to the UE through the RAN Node. The corenetwork can include a serving gateway (SGW), a packet data network (PDN)gateway (PGW), an access network detection and selection function(ANDSF) server, an enhanced packet data gateway (ePDG) and/or a mobilitymanagement entity (MME).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating the structure of a long termevolution (LTE) communication frame consistent with embodimentsdisclosed herein.

FIG. 2 is a flow chart illustrating a method for selecting a TimingError Limit consistent with embodiments disclosed herein.

FIG. 3 illustrates an architecture of a system of a network consistentwith embodiments disclosed herein.

FIG. 4 illustrates example components of a device consistent withembodiments disclosed herein.

FIG. 5 illustrates example interfaces of baseband circuitry consistentwith embodiments disclosed herein.

FIG. 6 is an illustration of a control plane protocol stack consistentwith embodiments disclosed herein.

FIG. 7 is a block diagram illustrating components able to readinstructions from a machine-readable or computer-readable medium andperform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

A detailed description of systems and methods consistent withembodiments of the present disclosure is provided below. While severalembodiments are described, it should be understood that the disclosureis not limited to any one embodiment, but instead encompasses numerousalternatives, modifications, and equivalents. In addition, whilenumerous specific details are set forth in the following description inorder to provide a thorough understanding of the embodiments disclosedherein, some embodiments can be practiced without some or all of thesedetails. Moreover, for the purpose of clarity, certain technicalmaterial that is known in the related art has not been described indetail in order to avoid unnecessarily obscuring the disclosure.

Techniques, apparatus and methods are disclosed that enable a UE toperform autonomous time adjustment, and select a Timing Error Limit(i.e. T_(e_NR)) and Maximum Autonomous Time Adjustment Step (i.e.T_(q_NR)) based on bandwidth (BW) and subcarrier spacing (SCS). In oneembodiment, given a certain downlink BW, if the SCS=x(kHz) and theT_(e_NR) of this SCS is N, then the T_(e_NR) of SCS=x/2 (kHz) is 2*N.Given a certain downlink BW, if the SCS=x(kHz) and the T_(e_NR) of thisSCS is N, then the T_(e_NR) of SCS=2*x(kHz) is N/2. For example, given aBW=10 MHz, if the T_(e_NR) of SCS=30 kHz is n*T_(s_NR) (T_(S_NR) is thebasic timing unit for NR system), then the T_(e_NR) of SCS=60 kHz isN/2*T_(s_NR), and the T_(e_NR) of SCS=15 kHz is 2*N*T_(s_NR).

In other embodiments, L, which can be 0 or a fixed margin, can be usedand/or scaled with N. In yet other embodiments, T_(e_NR) can bedetermined from a table when SCS is equal to or between two constraints.

The LTE UE has capability to automatically adjust its transmission (Tx)timing based on the receive (Rx) timing and estimated Tx timing. Forexample, the UE initial transmission timing error shall be less than orequal to ±T_(e) where the Timing Error Limit value T_(e) is specified inthe table below. This can apply when it is the first transmission in adiscontinuous reception (DRX), extended connected DRX (eDRX_CONN) cyclefor physical uplink control channel (PUCCH), physical uplink sharedchannel (PUSCH) and sounding reference signal (SRS) or it is the firsttransmission after random access channel (RACH)-less handover or it isthe physical random access channel (PRACH) transmission. The referencepoint for the UE initial transmit timing control can be the downlinktiming of the reference cell minus (N_(TA_Ref)+N_(TA offset))×T_(s). Thedownlink timing is defined as the time when the first detected path (intime) of the corresponding downlink frame is received from the referencecell. Timing reference (N_(TA_Ref)) for PRACH is defined as 0.(N_(TA_Ref)+N_(TA offset)(in T_(s) units) for other channels is thedifference between UE transmission timing and the downlink timingimmediately after when the last timing advance was applied. N_(TA_Ref)for other channels is not changed until the next timing advance isreceived.

T_(e) Timing Error Limit Downlink Bandwidth (MHz) T_(e) _(—) 1.4 24 *T_(S) ≥3 12 * T_(S) Note: T_(S) is the basic timing unit defined in TS36.211

When it is not the first transmission in a DRX or eDRX_CONN cycle orthere is no DRX or no eDRX_CONN cycle, and when it is the transmissionfor PUCCH, PUSCH and SRS transmission or it is not the firsttransmission after RACH-less handover, the UE shall be capable ofchanging the transmission timing according to the received downlinkframe of the reference cell except when a timing advance is applied.

When in a timing advance group (TAG) the transmission timing errorbetween the UE and the reference timing exceeds±T_(e), or in a sTAG theUE changes the downlink SCell for deriving the UE transmit timing forcells in the secondary TAG (sTAG) configured with one or two uplinks,the UE adjusts its timing to within ±T_(e) in that TAG, as long as theUE is configured with a primary TAG (pTAG) and one or two sTAGs, thetransmission timing difference between TAGs does not exceed the maximumtransmission timing difference (i.e., 32.47 μs) after such adjustment,or the UE is configured with synchronous dual connectivity, thetransmission timing difference between pTAG and sTAG does not exceed themaximum transmission timing difference (i.e., 35.21 μs) after suchadjustment.

If the transmission timing difference after such adjustment is biggerthan the maximum transmission timing difference, the UE may stopadjustment in this TAG. The reference timing shall be(N_(TA_Ref)+N_(TAoffset))×T_(s) before the downlink timing of thereference cell. All adjustments made to the UE uplink timing under theabove mentioned scenarios shall follow these rules: (1) the maximumamount of the magnitude of the timing change in one adjustment shall beT_(q) seconds; (2) the minimum aggregate adjustment rate shall be7*T_(S) per second; and (3) the maximum aggregate adjustment rate shallbe T_(q) per 200 ms, where the Maximum Autonomous Time Adjustment StepT_(q) is specified in the Table below.

T_(q) Maximum Autonomous Time Adjustment Step Downlink Bandwidth (MHz)T_(q) _(—) 1.4 17.5 * T_(S ) 3 9.5 * T_(S) 5 5.5 * T_(S) ≥10 3.5 * T_(S)Note: T_(S) is the basic timing unit defined in TS 36.211

T_(e) is the Timing Error Limit used to trigger the autonomous timeadjustment at the UE, and T_(q) is the Maximum Autonomous TimeAdjustment Step. In LTE both T_(e) and T_(q) are related with BW asshown in the above tables.

In NR systems, the UE is also capable of performing the autonomous timeadjustment, and it can determine or select the Timing Error Limit (i.e.T_(e_NR)) and Maximum Autonomous Time Adjustment Step (i.e. T_(q_NR)).However in NR systems, besides the BW there is another dimension ofsubcarrier spacing (SCS), and the new design of T_(e_NR) and T_(q_NR)consider the SCS as well as the BW.

The system for determining a Timing Error Limit or a Maximum AutonomousTime Adjustment Step can be determined as outlined in the followingembodiments. However, it should be recognized that the embodiments maystand alone or may be combined. For example, a first embodiment may beused for a set of SCS values above a threshold and a second embodimentmay be used for a set of SCS values below a threshold. In addition, anembodiment used to select a Timing Error Limit can be combined with anembodiment to select a Maximum Autonomous Time Adjustment Step in adifferent manner.

Embodiment 1: Timing Error Limit(i.e. T_(e_NR)) may be designeddifferently according to different SCS. Given a certain downlink BW, ifthe SCS=x(kHz) and the T_(e_NR) of this SCS is N, then the T_(e_NR) ofSCS=x/2 (kHz) is 2*N. Given a certain downlink BW, if the SCS=x(kHz) andthe T_(e_NR) of this SCS is N, then the T_(e_NR) of SCS=2*x(kHz) is N/2.

For example, given a BW=10 MHz, if the T_(e_NR) of SCS=30 kHz isn*T_(s_NR) (T_(S_NR) is the basic timing unit for NR system), then theT_(e_NR) of SCS=60 kHz is n/2*T_(s_NR), and the T_(e_NR) of SCS=15 kHzis 2*n*T_(s_NR).

Embodiment 2: Timing Error Limit (i.e. T_(e_NR)) may be designeddifferently according to different SCS. Given a certain downlink BW, ifthe SCS=x(kHz) and the T_(e_NR) of this SCS is N+L, then the T_(e_NR) ofSCS=x/2 (kHz) is 2*N+L; L is a fixed margin. Given a certain downlinkBW, if the SCS=x(kHz) and the T_(e_NR) of this SCS is N+L, then theT_(e_NR) of SCS=2*x(kHz) is N/2+L; L is a fixed margin.

For example, given a BW=10 MHz, if the T_(e_NR) of SCS=30 kHz is(N+L)*T_(s_NR), then the T_(e_NR) of SCS=60 kHz is (N/2+L)*T_(s_NR), andthe T_(e_NR) of SCS=15 kHz is (2*N+L)*T_(s_NR).

T_(e) _(—) _(NR) Timing Error Limit SCS (kHz) T_(e) _(—) _(NR) 15 (2 *N + L) * T_(S) _(—) _(NR) 30 (N + L) * T_(S) _(—) _(NR) ≥60 (N/2 + L) *T_(S) _(—) _(NR) Note: T_(S) _(—) _(NR) is the basic timing unit for NRsystem Note: L is a fixed value

Embodiment 3: Timing Error Limit (i.e. T_(e_NR)) may be designeddifferently according to different SCS. Given a certain downlink BW, ifthe SCS=x(kHz) and the T_(e_NR) of this SCS is N+L, then the T_(e_NR) ofSCS=x/2 (kHz) is 2*N+2*L; L is an SCS specific margin, e.g. L=N/2. Givena certain downlink BW, if the SCS=x(kHz) and the T_(e_NR) of this SCS isN+L, then the T_(e_NR) of SCS=2*x(kHz) is N/2+L/2; L is an SCS specificmargin, e.g. L=N/2.

For example, given a BW=10 MHz, if the T_(e_NR) of SCS=30 kHz is(N+L)*T_(s_NR), then the T_(e_NR) of SCS=60 kHz is (N/2+L/2)*T_(s_NR),and the T_(e_NR) of SCS=15 kHz is (2*N+2*L)*T_(s_NR); here the 1 may beequivalent to N/2.

Embodiment 4: Timing Error Limit (i.e. T_(e_NR)) may be designeddifferently according to different SCS, but the same T_(e_NR) may beapplied for some of the SCS levels. Given a certain downlink BW, the SCSrange is from x to y(kHz) and the T_(e_NR) of this SCS range may beimplemented as a same value: N.

For example, a table can be computed as shown below:

T_(e) _(—) _(NR) Timing Error Limit Subcarrier spacing (kHz) T_(e) _(—)_(NR) 15 N1 * T_(S) _(—) _(NR) 30 N2 * T_(S) _(—) _(NR) ≥60 N3 * T_(S)_(—) _(NR) Note: T_(S) _(—) _(NR) is the basic timing unit for NR systemNote: N1 > N2 > N3

Embodiment 5: Maximum Autonomous Time Adjustment Step (i.e. T_(q_NR))may be designed differently according to different SCS. Given a certaindownlink BW, if the SCS=x(kHz) and the T_(q_NR) of this SCS is N, thenthe T_(q_NR) of SCS=x/2 (kHz) is 2*N. Given a certain downlink BW, ifthe SCS=x(kHz) and the T_(q_NR) of this SCS is N, then the T_(q_NR) ofSCS=2*x(kHz) is N/2.

For example, given a BW=10 MHz, if the T_(q_NR) of SCS=30 kHz isn*T_(s_NR), then the T_(q_NR) of SCS=60 kHz is N/2*T_(s_NR), and theT_(q_NR) of SCS=15 kHz is 2*N*T_(s_NR).

Embodiment 6: Maximum Autonomous Time Adjustment Step (i.e. T_(q_NR))may be designed differently according to different SCS. Given a certaindownlink BW, if the SCS=x(kHz) and the T_(q_NR) of this SCS is N+L, thenthe T_(q_NR) of SCS=x/2 (kHz) is 2*N+L; L is a fixed margin. Given acertain downlink BW, if the SCS=x(kHz) and the T_(q_NR) of this SCS isN+L, then the T_(q_NR) of SCS=2*x(kHz) is N/2+L; L is a fixed margin.

For example, given a BW=10 MHz, if the T_(q_NR) of SCS=30 kHz is(N+L)*T_(s_NR), then the T_(q_NR) of SCS=60 kHz is (N/2+L)*T_(S_NR), andthe T_(q_NR) of SCS=15 kHz is (2*N+L)*T_(S_NR).

T_(q) _(—) _(NR) Maximum Autonomous Time Adjustment Step SCS (kHz) T_(q)_(—) _(NR) 15 (2 * N + L) * T_(S) _(—) _(NR) 30 (N + L) * T_(S) _(—)_(NR) ≥60 (N/2 + L) * T_(S) _(—) _(NR) Note: T_(S) _(—) _(NR) is thebasic timing unit for NR system Note: L is a fixed value

Embodiment 7: Maximum Autonomous Time Adjustment Step (i.e. T_(q_NR))may be designed differently according to different SCS. Given a certaindownlink BW, if the SCS=x(kHz) and the T_(q_NR) of this SCS is N+L, thenthe T_(q_R) of SCS=x/2 (kHz) is 2*N+2*L; L is an SCS specific margin,e.g. L=N/2. Given a certain downlink BW, if the SCS=x(kHz) and theT_(q_NR) of this SCS is N+L, then the T_(q_NR) of SCS=2*x(kHz) isN/2+L/2; L is an SCS specific margin, e.g. L=N/2.

For example, given a BW=10 MHz, if the T_(q_NR) of SCS=30 kHz is(N+L)*T_(s_NR), then the T_(q_NR) of SCS=60 kHz is (N/2+L/2)*T_(s_NR),and the T_(q_NR) of SCS=15 kHz is (2*N+2*L)*T_(s_NR); here the 1 may beequivalent to N/2.

Embodiment 8: Maximum Autonomous Time Adjustment Step (i.e. T_(q_NR))may be designed differently according to different SCS, but the sameT_(q_NR) may be applied for some of the SCS levels. Given a certaindownlink BW, the SCS range is from x to y(kHz) and the T_(q_NR) of thisSCS range may be implemented as a same value: N.

For example, the T_(q_NR) can be selected as shown in the table below:

T_(q) _(—) _(NR) Maximum Autonomous Time Adjustment Step SCS (kHz) T_(q)_(—) _(NR) 15 N1 * T_(S) _(—) _(NR) 30 N2 * T_(S) _(—) _(NR) ≥60 N3 *T_(S) _(—) _(NR) Note: T_(S) _(—) _(NR) is the basic timing unit for NRsystem Note: N1 > N2 > N3

Embodiment 9: Timing Error Limit (i.e. T_(e_NR)) may be designeddifferently according to different SCS. Given a certain downlink BW, alarger SCS level may have a smaller T_(e_NR), and a smaller SCS levelmay have a larger T_(e_NR).

For example, T_(e_NR) can be selected as shown in the table below:

T_(e)_NR Timing Error Limit Subcarrier spacing (kHz) T_(e NR) 15N1*T_(S NR) 30 N2*T_(S NR) 60 N3*T_(S NR) Note: T_(S)_NR is the basictiming unit for NR system Note: N1 > N2 > N3

Embodiment 10: Maximum Autonomous Time Adjustment Step (i.e. T_(q_NR))may be designed differently according to different SCS. Given a certaindownlink BW, a larger SCS level may have a smaller T_(q_NR), and asmaller SCS level may have a larger T_(q_NR).

For example, T_(q_NR) can be selected as shown in the table below:

T_(q) _(—) _(NR) Maximum Autonomous Time Adjustment Step SCS (kHz) T_(q)_(—) _(NR) 15 N1 * T_(S) _(—) _(NR) 30 N2 * T_(S) _(—) _(NR) 60 N3 *T_(S) _(—) _(NR) Note: T_(S) _(—) _(NR) is the basic timing unit for NRsystem Note: N1 > N2 > N3

FIG. 1 is a schematic diagram 100 illustrating the structure of an LTEcommunication frame 105. The frame 105 has a duration of 10 milliseconds(ms). The frame 105 includes 10 subframes 110, each having a duration of1 ms. Each subframe 110 includes two slots 115, each having a durationof 0.5 ms. Therefore, the frame 105 includes 20 slots 115.

Each slot 115 includes six or seven orthogonal frequency-divisionmultiplexing (OFDM) symbols 120. The number of OFDM symbols 120 in eachslot 115 is based on the size of cyclic prefixes (CP) 125. For example,the number of OFDM symbols 120 in the slot 115 is seven in normal modeCP and six in extended mode CP.

The smallest allocable unit for transmission is a resource block 130(i.e., physical resource block (PRB) 130). Transmissions are scheduledby the PRB 130. The PRB 130 consists of 12 consecutive subcarriers 135,or 180 kHz, for the duration of one slot 115 (0.5 ms). A resourceelement 140, which is the smallest defined unit, consists of one OFDMsubcarrier during one OFDM symbol interval. In the case of normal modeCP, each PRB 130 consists of 12×7=84 resource elements 140. Each PRB 130consists of 72 resource elements 140 in the case of extended mode CP(not shown).

In NR, SCS can be altered. For example, a subframe duration is fixed to1 ms and frame length is 10 ms. Scalable numerology allows at least from15 kHz to 480 kHz SCS. Numerologies with 15 kHz and larger SCS,regardless of CP overhead, align on symbol boundaries every 1 ms in anNR carrier.

In an embodiment, for the normal CP family, the following is adopted:For SCS of 15 kHz*2^(n) (n is non-negative integer), each symbol length(including CP) of 15 kHz SCS equals the sum of the corresponding 2^(n)symbols of the scaled SCS. Other than the first OFDM symbol in every 0.5ms, OFDM symbols within 0.5 ms have the same size. The first OFDM symbolin 0.5 ms is longer by 16T_(s) (assuming 15 kHz and FFT size of 2048)compared to other OFDM symbols. 16 T_(s) is used for CP for the firstsymbol.

For SCS of 15 kHz*2^(n) (n is a negative integer), each symbol length(including CP) of the SCS equals the sum of the corresponding 2^(−n)symbols of 15 kHz.

FIG. 2 is a flow chart illustrating a method 200 for selecting a TimingError Limit. The method 200 can be accomplished by systems such as thoseshown in FIG. 3, including a UE 301 and a UE 302. In block 202, the UEdetermines a reconfiguration event has occurred. In block 204, the UEdetermines a downlink (DL) bandwidth (BW) and a subcarrier spacing(SCS). In block 206, the UE selects a Timing Error Limit (T_(e_NR))based on the DL BW and the SCS, wherein the T_(e_NR)=N+L when SCS is x;wherein L is 0 or a fixed margin; wherein the T_(e_NR)≥2·N when SCS isx/2; and wherein the

$T_{e\_ NR} \geq \frac{N}{2}$when SCS is 2·x.

FIG. 3 illustrates an architecture of a system 300 of a network inaccordance with some embodiments. The system 300 is shown to include auser equipment (UE) 301 and a UE 302. The UEs 301 and 302 areillustrated as smartphones (e.g., handheld touchscreen mobile computingdevices connectable to one or more cellular networks), but may alsocomprise any mobile or non-mobile computing device, such as PersonalData Assistants (PDAs), pagers, laptop computers, desktop computers,wireless handsets, or any computing device including a wirelesscommunications interface.

In some embodiments, any of the UEs 301 and 302 can comprise an Internetof Things (IoT) UE, which can comprise a network access layer designedfor low-power IoT applications utilizing short-lived UE connections. AnIoT UE can utilize technologies such as machine-to-machine (M2M) ormachine-type communications (MTC) for exchanging data with an MTC serveror device via a public land mobile network (PLMN), Proximity-BasedService (ProSe) or device-to-device (D2D) communication, sensornetworks, or IoT networks. The M2M or MTC exchange of data may be amachine-initiated exchange of data. An IoT network describesinterconnecting IoT UEs, which may include uniquely identifiableembedded computing devices (within the Internet infrastructure), withshort-lived connections. The IoT UEs may execute background applications(e.g., keep-alive messages, status updates, etc.) to facilitate theconnections of the IoT network.

The UEs 301 and 302 may be configured to connect, e.g., communicativelycouple, with a radio access network (RAN) 310. The RAN 310 may be, forexample, an Evolved Universal Mobile Telecommunications System (UMTS)Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), orsome other type of RAN. The UEs 301 and 302 utilize connections 303 and304, respectively, each of which comprises a physical communicationsinterface or layer (discussed in further detail below); in this example,the connections 303 and 304 are illustrated as an air interface toenable communicative coupling, and can be consistent with cellularcommunications protocols, such as a Global System for MobileCommunications (GSM) protocol, a code-division multiple access (CDMA)network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular(POC) protocol, a Universal Mobile Telecommunications System (UMTS)protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation(5G) protocol, a New Radio (NR) protocol, and the like.

In this embodiment, the UEs 301 and 302 may further directly exchangecommunication data via a ProSe interface 305. The ProSe interface 305may alternatively be referred to as a sidelink interface comprising oneor more logical channels, including but not limited to a PhysicalSidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel(PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a PhysicalSidelink Broadcast Channel (PSBCH).

The UE 302 is shown to be configured to access an access point (AP) 306via connection 307. The connection 307 can comprise a local wirelessconnection, such as a connection consistent with any IEEE 802.11protocol, wherein the AP 306 would comprise a wireless fidelity (WiFi®)router. In this example, the AP 306 may be connected to the Internetwithout connecting to the core network of the wireless system (describedin further detail below).

The RAN 310 can include one or more access nodes that enable theconnections 303 and 304. These access nodes (ANs) can be referred to asbase stations (BSs), NodeBs, evolved NodeBs (eNBs), next GenerationNodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations(e.g., terrestrial access points) or satellite stations providingcoverage within a geographic area (e.g., a cell). The RAN 310 mayinclude one or more RAN nodes for providing macrocells, e.g., macro RANnode 311, and one or more RAN nodes for providing femtocells orpicocells (e.g., cells having smaller coverage areas, smaller usercapacity, or higher bandwidth compared to macrocells), e.g., low power(LP) RAN node 312.

Any of the RAN nodes 311 and 312 can terminate the air interfaceprotocol and can be the first point of contact for the UEs 301 and 302.In some embodiments, any of the RAN nodes 311 and 312 can fulfillvarious logical functions for the RAN 310 including, but not limited to,radio network controller (RNC) functions such as radio bearermanagement, uplink and downlink dynamic radio resource management anddata packet scheduling, and mobility management.

In accordance with some embodiments, the UEs 301 and 302 can beconfigured to communicate using Orthogonal Frequency-DivisionMultiplexing (OFDM) communication signals with each other or with any ofthe RAN nodes 311 and 312 over a multicarrier communication channel inaccordance various communication techniques, such as, but not limitedto, an Orthogonal Frequency-Division Multiple Access (OFDMA)communication technique (e.g., for downlink communications) or a SingleCarrier Frequency Division Multiple Access (SC-FDMA) communicationtechnique (e.g., for uplink and ProSe or sidelink communications),although the scope of the embodiments is not limited in this respect.The OFDM signals can comprise a plurality of orthogonal subcarriers.

In some embodiments, a downlink resource grid can be used for downlinktransmissions from any of the RAN nodes 311 and 312 to the UEs 301 and302, while uplink transmissions can utilize similar techniques. The gridcan be a time-frequency grid, called a resource grid or time-frequencyresource grid, which is the physical resource in the downlink in eachslot. Such a time-frequency plane representation is a common practicefor OFDM systems, which makes it intuitive for radio resourceallocation. Each column and each row of the resource grid corresponds toone OFDM symbol and one OFDM subcarrier, respectively. The duration ofthe resource grid in the time domain corresponds to one slot in a radioframe. The smallest time-frequency unit in a resource grid is denoted asa resource element. Each resource grid comprises a number of resourceblocks, which describe the mapping of certain physical channels toresource elements. Each resource block comprises a collection ofresource elements; in the frequency domain, this may represent thesmallest quantity of resources that currently can be allocated. Thereare several different physical downlink channels that are conveyed usingsuch resource blocks.

The physical downlink shared channel (PDSCH) may carry user data andhigher-layer signaling to the UEs 301 and 302. The physical downlinkcontrol channel (PDCCH) may carry information about the transport formatand resource allocations related to the PDSCH channel, among otherthings. It may also inform the UEs 301 and 302 about the transportformat, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request)information related to the uplink shared channel. Typically, downlinkscheduling (assigning control and shared channel resource blocks to theUE 302 within a cell) may be performed at any of the RAN nodes 311 and312 based on channel quality information fed back from any of the UEs301 and 302. The downlink resource assignment information may be sent onthe PDCCH used for (e.g., assigned to) each of the UEs 301 and 302.

The PDCCH may use control channel elements (CCEs) to convey the controlinformation. Before being mapped to resource elements, the PDCCHcomplex-valued symbols may first be organized into quadruplets, whichmay then be permuted using a sub-block interleaver for rate matching.Each PDCCH may be transmitted using one or more of these CCEs, whereeach CCE may correspond to nine sets of four physical resource elementsknown as resource element groups (REGs). Four Quadrature Phase ShiftKeying (QPSK) symbols may be mapped to each REG. The PDCCH can betransmitted using one or more CCEs, depending on the size of thedownlink control information (DCI) and the channel condition. There canbe four or more different PDCCH formats defined in LTE with differentnumbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

Some embodiments may use concepts for resource allocation for controlchannel information that are an extension of the above-describedconcepts. For example, some embodiments may utilize an enhanced physicaldownlink control channel (EPDCCH) that uses PDSCH resources for controlinformation transmission. The EPDCCH may be transmitted using one ormore enhanced the control channel elements (ECCEs). Similar to above,each ECCE may correspond to nine sets of four physical resource elementsknown as enhanced resource element groups (EREGs). An ECCE may haveother numbers of EREGs in some situations.

The RAN 310 is shown to be communicatively coupled to a core network(CN) 320—via an S1 interface 313. In embodiments, the CN 320 may be anevolved packet core (EPC) network, a NextGen Packet Core (NPC) network,or some other type of CN. In this embodiment the S1 interface 313 issplit into two parts: the S1-U interface 314, which carries traffic databetween the RAN nodes 311 and 312 and a serving gateway (S-GW) 322, andan S1-mobility management entity (MME) interface 315, which is asignaling interface between the RAN nodes 311 and 312 and MMEs 321.

In this embodiment, the CN 320 comprises the MMEs 321, the S-GW 322, aPacket Data Network (PDN) Gateway (P-GW) 323, and a home subscriberserver (HSS) 324. The MMEs 321 may be similar in function to the controlplane of legacy Serving General Packet Radio Service (GPRS) SupportNodes (SGSN). The MMEs 321 may manage mobility aspects in access such asgateway selection and tracking area list management. The HSS 324 maycomprise a database for network users, including subscription-relatedinformation to support the network entities' handling of communicationsessions. The CN 320 may comprise one or several HSSs 324, depending onthe number of mobile subscribers, on the capacity of the equipment, onthe organization of the network, etc. For example, the HSS 324 canprovide support for routing/roaming, authentication, authorization,naming/addressing resolution, location dependencies, etc.

The S-GW 322 may terminate the S1 interface 313 towards the RAN 310, androutes data packets between the RAN 310 and the CN 320. In addition, theS-GW 322 may be a local mobility anchor point for inter-RAN nodehandovers and also may provide an anchor for inter-3GPP mobility. Otherresponsibilities may include lawful intercept, charging, and some policyenforcement.

The P-GW 323 may terminate an SGi interface toward a PDN. The P-GW 323may route data packets between the CN 320 (e.g., an EPC network) andexternal networks such as a network including the application server 330(alternatively referred to as application function (AF)) via an InternetProtocol (IP) interface 325. Generally, an application server 330 may bean element offering applications that use IP bearer resources with thecore network (e.g., UMTS Packet Services (PS) domain, LTE PS dataservices, etc.). In this embodiment, the P-GW 323 is shown to becommunicatively coupled to an application server 330 via an IPcommunications interface 325. The application server 330 can also beconfigured to support one or more communication services (e.g.,Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, groupcommunication sessions, social networking services, etc.) for the UEs301 and 302 via the CN 320.

The P-GW 323 may further be a node for policy enforcement and chargingdata collection. A Policy and Charging Enforcement Function (PCRF) 326is the policy and charging control element of the CN 320. In anon-roaming scenario, there may be a single PCRF in the Home Public LandMobile Network (HPLMN) associated with a UE's Internet ProtocolConnectivity Access Network (IP-CAN) session. In a roaming scenario withlocal breakout of traffic, there may be two PCRFs associated with a UE'sIP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF(V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF326 may be communicatively coupled to the application server 330 via theP-GW 323. The application server 330 may signal the PCRF 326 to indicatea new service flow and select the appropriate Quality of Service (QoS)and charging parameters. The PCRF 326 may provision this rule into aPolicy and Charging Enforcement Function (PCEF) (not shown) with theappropriate traffic flow template (TFT) and QoS class of identifier(QCI), which commences the QoS and charging as specified by theapplication server 330.

FIG. 4 illustrates example components of a device 400 in accordance withsome embodiments. In some embodiments, the device 400 may includeapplication circuitry 402, baseband circuitry 404, Radio Frequency (RF)circuitry 406, front-end module (FEM) circuitry 408, one or moreantennas 410, and power management circuitry (PMC) 412 coupled togetherat least as shown. The components of the illustrated device 400 may beincluded in a UE or a RAN node. In some embodiments, the device 400 mayinclude fewer elements (e.g., a RAN node may not utilize applicationcircuitry 402, and instead include a processor/controller to process IPdata received from an EPC). In some embodiments, the device 400 mayinclude additional elements such as, for example, memory/storage,display, camera, sensor, or input/output (I/O) interface. In otherembodiments, the components described below may be included in more thanone device (e.g., said circuitries may be separately included in morethan one device for Cloud-RAN (C-RAN) implementations).

The application circuitry 402 may include one or more applicationprocessors. For example, the application circuitry 402 may includecircuitry such as, but not limited to, one or more single-core ormulti-core processors. The processor(s) may include any combination ofgeneral-purpose processors and dedicated processors (e.g., graphicsprocessors, application processors, etc.). The processors may be coupledwith or may include memory/storage and may be configured to executeinstructions stored in the memory/storage to enable various applicationsor operating systems to run on the device 400. In some embodiments,processors of application circuitry 402 may process IP data packetsreceived from an EPC.

The baseband circuitry 404 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Thebaseband circuitry 404 may include one or more baseband processors orcontrol logic to process baseband signals received from a receive signalpath of the RF circuitry 406 and to generate baseband signals for atransmit signal path of the RF circuitry 406. Baseband processingcircuity 404 may interface with the application circuitry 402 forgeneration and processing of the baseband signals and for controllingoperations of the RF circuitry 406. For example, in some embodiments,the baseband circuitry 404 may include a third generation (3G) basebandprocessor 404A, a fourth generation (4G) baseband processor 404B, afifth generation (5G) baseband processor 404C, or other basebandprocessor(s) 404D for other existing generations, generations indevelopment or to be developed in the future (e.g., second generation(2G), sixth generation (6G), etc.). The baseband circuitry 404 (e.g.,one or more of baseband processors 404A-D) may handle various radiocontrol functions that enable communication with one or more radionetworks via the RF circuitry 406. In other embodiments, some or all ofthe functionality of baseband processors 404A-D may be included inmodules stored in the memory 404G and executed via a Central ProcessingUnit (CPU) 404E. The radio control functions may include, but are notlimited to, signal modulation/demodulation, encoding/decoding, radiofrequency shifting, etc. In some embodiments, modulation/demodulationcircuitry of the baseband circuitry 404 may include Fast-FourierTransform (FFT), precoding, or constellation mapping/demappingfunctionality. In some embodiments, encoding/decoding circuitry of thebaseband circuitry 404 may include convolution, tail-biting convolution,turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoderfunctionality. Embodiments of modulation/demodulation andencoder/decoder functionality are not limited to these examples and mayinclude other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry 404 may include one or moreaudio digital signal processor(s) (DSP) 404F. The audio DSP(s) 404F maybe include elements for compression/decompression and echo cancellationand may include other suitable processing elements in other embodiments.Components of the baseband circuitry may be suitably combined in asingle chip, a single chipset, or disposed on a same circuit board insome embodiments. In some embodiments, some or all of the constituentcomponents of the baseband circuitry 404 and the application circuitry402 may be implemented together such as, for example, on a system on achip (SOC).

In some embodiments, the baseband circuitry 404 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 404 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) or other wireless metropolitan area networks (WMAN), a wirelesslocal area network (WLAN), or a wireless personal area network (WPAN).Embodiments in which the baseband circuitry 404 is configured to supportradio communications of more than one wireless protocol may be referredto as multi-mode baseband circuitry.

RF circuitry 406 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 406 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. The RF circuitry 406 may include a receive signal path whichmay include circuitry to down-convert RF signals received from the FEMcircuitry 408 and provide baseband signals to the baseband circuitry404. RF circuitry 406 may also include a transmit signal path which mayinclude circuitry to up-convert baseband signals provided by thebaseband circuitry 404 and provide RF output signals to the FEMcircuitry 408 for transmission.

In some embodiments, the receive signal path of the RF circuitry 406 mayinclude mixer circuitry 406A, amplifier circuitry 406B and filtercircuitry 406C. In some embodiments, the transmit signal path of the RFcircuitry 406 may include filter circuitry 406C and mixer circuitry406A. RF circuitry 406 may also include synthesizer circuitry 406D forsynthesizing a frequency for use by the mixer circuitry 406A of thereceive signal path and the transmit signal path. In some embodiments,the mixer circuitry 406A of the receive signal path may be configured todown-convert RF signals received from the FEM circuitry 408 based on thesynthesized frequency provided by synthesizer circuitry 406D. Theamplifier circuitry 406B may be configured to amplify the down-convertedsignals and the filter circuitry 406C may be a low-pass filter (LPF) orband-pass filter (BPF) configured to remove unwanted signals from thedown-converted signals to generate output baseband signals. Outputbaseband signals may be provided to the baseband circuitry 404 forfurther processing. In some embodiments, the output baseband signals maybe zero-frequency baseband signals, although this is not a requirement.In some embodiments, the mixer circuitry 406A of the receive signal pathmay comprise passive mixers, although the scope of the embodiments isnot limited in this respect.

In some embodiments, the mixer circuitry 406A of the transmit signalpath may be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 406D togenerate RF output signals for the FEM circuitry 408. The basebandsignals may be provided by the baseband circuitry 404 and may befiltered by the filter circuitry 406C.

In some embodiments, the mixer circuitry 406A of the receive signal pathand the mixer circuitry 406A of the transmit signal path may include twoor more mixers and may be arranged for quadrature downconversion andupconversion, respectively. In some embodiments, the mixer circuitry406A of the receive signal path and the mixer circuitry 406A of thetransmit signal path may include two or more mixers and may be arrangedfor image rejection (e.g., Hartley image rejection). In someembodiments, the mixer circuitry 406A of the receive signal path and themixer circuitry 406A may be arranged for direct downconversion anddirect upconversion, respectively. In some embodiments, the mixercircuitry 406A of the receive signal path and the mixer circuitry 406Aof the transmit signal path may be configured for super-heterodyneoperation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, the RFcircuitry 406 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry404 may include a digital baseband interface to communicate with the RFcircuitry 406.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 406D may be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the embodiments is not limited in this respect as other typesof frequency synthesizers may be suitable. For example, synthesizercircuitry 406D may be a delta-sigma synthesizer, a frequency multiplier,or a synthesizer comprising a phase-locked loop with a frequencydivider.

The synthesizer circuitry 406D may be configured to synthesize an outputfrequency for use by the mixer circuitry 406A of the RF circuitry 406based on a frequency input and a divider control input. In someembodiments, the synthesizer circuitry 406D may be a fractional N/N+1synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 404 orthe application circuitry 402 (such as an applications processor)depending on the desired output frequency. In some embodiments, adivider control input (e.g., N) may be determined from a look-up tablebased on a channel indicated by the application circuitry 402.

Synthesizer circuitry 406D of the RF circuitry 406 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some embodiments, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some embodiments, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example embodiments, theDLL may include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. In these embodiments,the delay elements may be configured to break a VCO period up into Ndequal packets of phase, where Nd is the number of delay elements in thedelay line. In this way, the DLL provides negative feedback to helpensure that the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuitry 406D may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someembodiments, the output frequency may be a LO frequency (fLO). In someembodiments, the RF circuitry 406 may include an IQ/polar converter.

FEM circuitry 408 may include a receive signal path which may includecircuitry configured to operate on RF signals received from one or moreantennas 410, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 406 for furtherprocessing. The FEM circuitry 408 may also include a transmit signalpath which may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 406 for transmission by one ormore of the one or more antennas 410. In various embodiments, theamplification through the transmit or receive signal paths may be donesolely in the RF circuitry 406, solely in the FEM circuitry 408, or inboth the RF circuitry 406 and the FEM circuitry 408.

In some embodiments, the FEM circuitry 408 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry 408 may include a receive signal path and a transmit signalpath. The receive signal path of the FEM circuitry 408 may include anLNA to amplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 406). The transmitsignal path of the FEM circuitry 408 may include a power amplifier (PA)to amplify input RF signals (e.g., provided by the RF circuitry 406),and one or more filters to generate RF signals for subsequenttransmission (e.g., by one or more of the one or more antennas 410).

In some embodiments, the PMC 412 may manage power provided to thebaseband circuitry 404. In particular, the PMC 412 may controlpower-source selection, voltage scaling, battery charging, or DC-to-DCconversion. The PMC 412 may often be included when the device 400 iscapable of being powered by a battery, for example, when the device 400is included in a UE. The PMC 412 may increase the power conversionefficiency while providing desirable implementation size and heatdissipation characteristics.

FIG. 4 shows the PMC 412 coupled only with the baseband circuitry 404.However, in other embodiments, the PMC 412 may be additionally oralternatively coupled with, and perform similar power managementoperations for, other components such as, but not limited to, theapplication circuitry 402, the RF circuitry 406, or the FEM circuitry408.

In some embodiments, the PMC 412 may control, or otherwise be part of,various power saving mechanisms of the device 400. For example, if thedevice 400 is in an RRC_Connected state, where it is still connected tothe RAN node as it expects to receive traffic shortly, then it may entera state known as Discontinuous Reception Mode (DRX) after a period ofinactivity. During this state, the device 400 may power down for briefintervals of time and thus save power.

If there is no data traffic activity for an extended period of time,then the device 400 may transition off to an RRC_Idle state, where itdisconnects from the network and does not perform operations such aschannel quality feedback, handover, etc. The device 400 goes into a verylow power state and it performs paging where again it periodically wakesup to listen to the network and then powers down again. The device 400may not receive data in this state, and in order to receive data, ittransitions back to an RRC_Connected state.

An additional power saving mode may allow a device to be unavailable tothe network for periods longer than a paging interval (ranging fromseconds to a few hours). During this time, the device is totallyunreachable to the network and may power down completely. Any data sentduring this time incurs a large delay and it is assumed the delay isacceptable.

Processors of the application circuitry 402 and processors of thebaseband circuitry 404 may be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 404, alone or in combination, may be used to execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 402 may utilize data (e.g., packet data) received from theselayers and further execute Layer 4 functionality (e.g., transmissioncommunication protocol (TCP) and user datagram protocol (UDP) layers).As referred to herein, Layer 3 may comprise a radio resource control(RRC) layer, described in further detail below. As referred to herein,Layer 2 may comprise a medium access control (MAC) layer, a radio linkcontrol (RLC) layer, and a packet data convergence protocol (PDCP)layer, described in further detail below. As referred to herein, Layer 1may comprise a physical (PHY) layer of a UE/RAN node, described infurther detail below.

FIG. 5 illustrates example interfaces of baseband circuitry inaccordance with some embodiments. As discussed above, the basebandcircuitry 404 of FIG. 4 may comprise processors 404A-404E and a memory404G utilized by said processors. Each of the processors 404A-404E mayinclude a memory interface, 504A-504E, respectively, to send/receivedata to/from the memory 404G.

The baseband circuitry 404 may further include one or more interfaces tocommunicatively couple to other circuitries/devices, such as a memoryinterface 512 (e.g., an interface to send/receive data to/from memoryexternal to the baseband circuitry 404), an application circuitryinterface 514 (e.g., an interface to send/receive data to/from theapplication circuitry 402 of FIG. 4), an RF circuitry interface 516(e.g., an interface to send/receive data to/from RF circuitry 406 ofFIG. 4), a wireless hardware connectivity interface 518 (e.g., aninterface to send/receive data to/from Near Field Communication (NFC)components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi®components, and other communication components), and a power managementinterface 520 (e.g., an interface to send/receive power or controlsignals to/from the PMC 412.

FIG. 6 is an illustration of a control plane protocol stack inaccordance with some embodiments. In this embodiment, a control plane600 is shown as a communications protocol stack between the UE 301 (oralternatively, the UE 302), the RAN node 311 (or alternatively, the RANnode 312), and the MME 321.

A PHY layer 601 may transmit or receive information used by the MAClayer 602 over one or more air interfaces. The PHY layer 601 may furtherperform link adaptation or adaptive modulation and coding (AMC), powercontrol, cell search (e.g., for initial synchronization and handoverpurposes), and other measurements used by higher layers, such as an RRClayer 605. The PHY layer 601 may still further perform error detectionon the transport channels, forward error correction (FEC)coding/decoding of the transport channels, modulation/demodulation ofphysical channels, interleaving, rate matching, mapping onto physicalchannels, and Multiple Input Multiple Output (MIMO) antenna processing.

The MAC layer 602 may perform mapping between logical channels andtransport channels, multiplexing of MAC service data units (SDUs) fromone or more logical channels onto transport blocks (TB) to be deliveredto PHY via transport channels, de-multiplexing MAC SDUs to one or morelogical channels from transport blocks (TB) delivered from the PHY viatransport channels, multiplexing MAC SDUs onto TBs, schedulinginformation reporting, error correction through hybrid automatic repeatrequest (HARD), and logical channel prioritization.

An RLC layer 603 may operate in a plurality of modes of operation,including: Transparent Mode (TM), Unacknowledged Mode (UM), andAcknowledged Mode (AM). The RLC layer 603 may execute transfer of upperlayer protocol data units (PDUs), error correction through automaticrepeat request (ARQ) for AM data transfers, and concatenation,segmentation and reassembly of RLC SDUs for UM and AM data transfers.The RLC layer 603 may also execute re-segmentation of RLC data PDUs forAM data transfers, reorder RLC data PDUs for UM and AM data transfers,detect duplicate data for UM and AM data transfers, discard RLC SDUs forUM and AM data transfers, detect protocol errors for AM data transfers,and perform RLC re-establishment.

A PDCP layer 604 may execute header compression and decompression of IPdata, maintain PDCP Sequence Numbers (SNs), perform in-sequence deliveryof upper layer PDUs at re-establishment of lower layers, eliminateduplicates of lower layer SDUs at re-establishment of lower layers forradio bearers mapped on RLC AM, cipher and decipher control plane data,perform integrity protection and integrity verification of control planedata, control timer-based discard of data, and perform securityoperations (e.g., ciphering, deciphering, integrity protection,integrity verification, etc.).

The main services and functions of the RRC layer 605 may includebroadcast of system information (e.g., included in Master InformationBlocks (MIBs) or System Information Blocks (SIBs) related to thenon-access stratum (NAS)), broadcast of system information related tothe access stratum (AS), paging, establishment, maintenance and releaseof an RRC connection between the UE and E-UTRAN (e.g., RRC connectionpaging, RRC connection establishment, RRC connection modification, andRRC connection release), establishment, configuration, maintenance andrelease of point-to-point radio bearers, security functions includingkey management, inter radio access technology (RAT) mobility, andmeasurement configuration for UE measurement reporting. Said MIBs andSIBs may comprise one or more information elements (IEs), which may eachcomprise individual data fields or data structures.

The UE 301 and the RAN node 311 may utilize a Uu interface (e.g., anLTE-Uu interface) to exchange control plane data via a protocol stackcomprising the PHY layer 601, the MAC layer 602, the RLC layer 603, thePDCP layer 604, and the RRC layer 605.

In the embodiment shown, the non-access stratum (NAS) protocols 606 formthe highest stratum of the control plane between the UE 301 and the MME321. The NAS protocols 606 support the mobility of the UE 301 and thesession management procedures to establish and maintain IP connectivitybetween the UE 301 and the P-GW 323.

The S1 Application Protocol (S1-AP) layer 615 may support the functionsof the S1 interface and comprise Elementary Procedures (EPs). An EP is aunit of interaction between the RAN node 311 and the CN 320. The S1-APlayer services may comprise two groups: UE-associated services and nonUE-associated services. These services perform functions including, butnot limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UEcapability indication, mobility, NAS signaling transport, RANInformation Management (RIM), and configuration transfer.

The Stream Control Transmission Protocol (SCTP) layer (alternativelyreferred to as the stream control transmission protocol/internetprotocol (SCTP/IP) layer) 614 may ensure reliable delivery of signalingmessages between the RAN node 311 and the MME 321 based, in part, on theIP protocol, supported by an IP layer 613. An L2 layer 612 and an L1layer 611 may refer to communication links (e.g., wired or wireless)used by the RAN node and the MME to exchange information.

The RAN node 311 and the MME 321 may utilize an S1-MME interface toexchange control plane data via a protocol stack comprising the L1 layer611, the L2 layer 612, the IP layer 613, the SCTP layer 614, and theS1-AP layer 615.

FIG. 7 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein. Specifically, FIG. 7 shows a diagrammaticrepresentation of hardware resources 700 including one or moreprocessors (or processor cores) 710, one or more memory/storage devices720, and one or more communication resources 730, each of which may becommunicatively coupled via a bus 740. For embodiments where nodevirtualization (e.g., NFV) is utilized, a hypervisor 702 may be executedto provide an execution environment for one or more networkslices/sub-slices to utilize the hardware resources 700.

The processors 710 (e.g., a central processing unit (CPU), a reducedinstruction set computing (RISC) processor, a complex instruction setcomputing (CISC) processor, a graphics processing unit (GPU), a digitalsignal processor (DSP) such as a baseband processor, an applicationspecific integrated circuit (ASIC), a radio-frequency integrated circuit(RFIC), another processor, or any suitable combination thereof) mayinclude, for example, a processor 712 and a processor 714.

The memory/storage devices 720 may include main memory, disk storage, orany suitable combination thereof. The memory/storage devices 720 mayinclude, but are not limited to any type of volatile or non-volatilememory such as dynamic random access memory (DRAM), static random-accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), Flashmemory, solid-state storage, etc.

The communication resources 730 may include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 704 or one or more databases 706 via anetwork 708. For example, the communication resources 730 may includewired communication components (e.g., for coupling via a UniversalSerial Bus (USB)), cellular communication components, NFC components,Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components,and other communication components.

Instructions 750 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 710 to perform any one or more of the methodologies discussedherein. The instructions 750 may reside, completely or partially, withinat least one of the processors 710 (e.g., within the processor's cachememory), the memory/storage devices 720, or any suitable combinationthereof. Furthermore, any portion of the instructions 750 may betransferred to the hardware resources 700 from any combination of theperipheral devices 704 or the databases 706. Accordingly, the memory ofprocessors 710, the memory/storage devices 720, the peripheral devices704, and the databases 706 are examples of computer-readable andmachine-readable media.

EXAMPLES

The following examples pertain to further embodiments.

Example 1 is an apparatus for a user equipment (UE), comprising: awireless interface and a processor. The wireless interface configured tocommunicate with a radio access network (RAN) node. The processor iscoupled to the wireless interface, and the processor configured to:determine a reconfiguration event has occurred; determine a downlink(DL) bandwidth (BW) and a subcarrier spacing (SCS); and select a timingerror limit(T_(e_NR)) based on the DL BW and the SCS, wherein theT_(e_NR)=N+L when SCS is x, wherein L is 0 or a fixed margin; whereinthe T_(e_NR)≥2·N when SCS is

$\frac{x}{2};$and wherein the

$T_{e\;\_\;{NR}} \geq \frac{N}{2}$when SCS is 2·x.

Example 2 is the apparatus of Example 1, wherein reconfiguration eventis a network reconfiguration.

Example 3 is the apparatus of Example 1, wherein the reconfigurationevent is a mobility event.

Example 4 is the apparatus of Example 3, wherein the mobility event is ahandover.

Example 5 is the apparatus of Example 1, wherein the

$T_{e\;\_\;{NR}} = {\frac{N}{2} + L}$when SCS is 2·x, where L is a fixed margin.

Example 6 is the apparatus of Example 1, wherein the T_(e_NR)=2·N+L whenSCS is

$\frac{x}{2},$where L is a fixed margin.

Example 7 is the apparatus of Example 1, wherein the

$T_{e\;\_\;{NR}} = {\frac{N}{2} + \frac{L}{2}}$when SCS is 2·x, where L is a fixed margin.

Example 8 is the apparatus of Example 1, wherein the T_(e_NR)=2·N+2·Lwhen SCS is

$\frac{x}{2},$where L is a fixed margin.

Example 9 is the apparatus of any of Examples 1-4, wherein the processoris a baseband processor.

Example 10 is a system for determining a maximum autonomous timeadjustment step (T_(q_NR)) comprising: storage for T_(q_NR); and aprocessor configured to: determine a reconfiguration event has occurred;determine a downlink (DL) bandwidth (BW) and a subcarrier spacing (SCS);and select T_(q_NR) based on the DL BW and the SCS, wherein theT_(q_NR)=N+L when SCS is x, wherein L is 0 or a fixed margin; whereinthe T_(q_NR)≥2·N when SCS is

$\frac{x}{2};$and wherein the

$T_{q\;\_\;{NR}} \geq \frac{N}{2}$when SCS is 2·x.

Example 11 is the system of Example 10, wherein the system is anapparatus of a user equipment (UE).

Example 12 is the system of Example 10, wherein the reconfigurationevent is a network reconfiguration.

Example 13 is the system of Example 10, wherein the reconfigurationevent is a mobility event.

Example 14 is the system of Example 10, wherein the mobility event is ahandover.

Example 15 is the system of Example 10, wherein the

$T_{q\;\_\;{NR}} = {\frac{N}{2} + L}$when SCS is 2·x, where L is a fixed margin.

Example 16 is the system of Example 10, wherein the T_(q_NR)=2·N+L whenSCS is

$\frac{x}{2},$where L is a fixed margin.

Example 17 is the system of Example 10, wherein the

$T_{q\;\_\;{NR}} = {\frac{N}{2} + \frac{L}{2}}$when SCS is 2·x, where L is a fixed margin.

Example 18 is the system of Example 10, wherein the T_(q_NR)=2·N+2·Lwhen SCS is

$\frac{x}{2},$where L is a fixed margin.

Example 19 is the system of any of Examples 10-18, wherein the processoris a baseband processor.

Example 20 is a computer program product comprising a computer-readablestorage medium that stores instructions for execution by a processor toperform operations of a user equipment (UE), the operations, whenexecuted by the processor, to perform a method, the method comprising:determining a reconfiguration event has occurred; determining a downlink(DL) bandwidth (BW) and a subcarrier spacing (SCS); and selecting atiming error limit(T_(e_NR)) based on the DL BW and the SCS, wherein theT_(e_NR)=(N+L)·T_(S_NR) when SCS is x, wherein L is 0 or a fixed margin,wherein T_(S_NR) is a basic timing unit for a new radio (NR) cellularsystem; wherein the T_(e_NR)≥(2·N+L)·T_(S_NR) when SCS is

$\frac{x}{2};$and wherein the

$T_{e\;\_\;{NR}} \geq {\left( {\frac{N}{2} + L} \right) \cdot T_{S\;\_\;{NR}}}$when SCS is 2·x.

Example 21 is the computer program product of Example 20, whereinselecting T_(e_NR) further comprises selecting T_(e_NR) from a tablebased on BW and SCS being between two values or equal to one of the twovalues.

Example 22 is the computer program product of Example 20, wherein the

$T_{e\;\_\;{NR}} = {\left( {\frac{N}{2} + L} \right) \cdot T_{S\;\_\;{NR}}}$when SCS is 2·x, and where L is a fixed margin.

Example 23 is the computer program product of Example 20, wherein the

$T_{e\;\_\;{NR}} = {\left( {\frac{N}{2} + \frac{L}{2}} \right) \cdot T_{S\;\_\;{NR}}}$when SCS is 2·x, and where L is a fixed margin.

Example 24 is an apparatus for determining a timing error limit in acellular system, the apparatus comprising: means for determining areconfiguration event has occurred; means for determining a downlink(DL) bandwidth (BW) and a subcarrier spacing (SCS); and means forselecting a timing error limit(T_(e_NR)) based on the DL BW and the SCS,wherein the T_(e_NR)=N+L when SCS is x, wherein L is 0 or a fixedmargin; wherein the T_(e_NR)≥2·N when SCS is

$\frac{x}{2};$and wherein the

$T_{e\;\_\;{NR}} \geq \frac{N}{2}$when SCS is 2·x.

Example 25 is a method of determining a timing error limit in a cellularsystem, the method comprising: determining a reconfiguration event hasoccurred; determining a downlink (DL) bandwidth (BW) and a subcarrierspacing (SCS); and selecting a timing error limit(T_(e_NR)) based on theDL BW and the SCS, wherein the T_(e_NR)=N+L when SCS is x,

wherein L is 0 or a fixed margin; wherein the T_(e_NR)≥2·N when SCS is

$\frac{x}{2};$and wherein the

$T_{e\;\_\;{NR}} \geq \frac{N}{2}$when SCS is 2·x.

ADDITIONAL EXAMPLES

Additional Example 1 may include: the Timing Error Limit (i.e. T_(e_NR))may be designed differently according to different SCS. Given a certaindownlink bandwidth (BW), if the SCS=x(kHz) and the T_(e_NR) of this SCSis N, then the

${T_{e\;\_\;{NR}}\mspace{14mu}{of}\mspace{14mu}{SCS}} = {\frac{x}{2}({kHz})}$is 2*N.

Given a certain downlink BW, if the SCS=x(kHz) and the T_(e_NR) of thisSCS is N, then the

${T_{e\;\_\;{NR}}\mspace{14mu}{of}\mspace{14mu}{SCS}} = {2^{*}{x({kHz})}\mspace{14mu}{is}\mspace{14mu}{\frac{N}{2}.}}$

Additional Example 2 may include: the Timing Error Limit (i.e. T_(e_NR))may be designed differently according to different SCS. Given a certaindownlink BW, if the SCS=x(kHz) and the T_(e_NR) of this SCS is N+L, thenthe T_(e_NR) of

${SCS} = {\frac{x}{2}({kHz})}$is 2*N+L; L is a fixed margin. Given a certain downlink BW, if theSCS=x(kHz) and the T_(e_NR) of this SCS is N+L, then the T_(e_NR) of

${{SCS} = {{2^{*}{x({kHz})}\mspace{14mu}{is}\mspace{14mu}\frac{N}{2}} + L}};$L is a fixed margin.

Additional Example 3 may include: Timing Error Limit (i.e. T_(e_NR)) maybe designed differently according to different SCS. Given a certaindownlink BW, if the SCS=x(kHz) and the T_(e_NR) of this SCS is N+L, thenthe T_(e_NR) of

${SCS} = {\frac{x}{2}({kHz})}$is 2*N+2*L; L is an SCS specific margin, e.g.

$L = {\frac{N}{2}.}$Given a certain downlink BW, if the SCS=x(kHz) and the T_(e_NR) of thisSCS is N+L, then the T_(e_NR) of SCS=2*x(kHz) is

${\frac{N}{2} + \frac{L}{2}};$L is an SCS specific margin, e.g.

$L = {\frac{N}{2}.}$

Additional Example 4 may include: Timing Error Limit (i.e. T_(e_NR)) maybe designed differently according to different SCS, but same T_(e_NR)may be applied for some of the SCS levels. Given a certain downlink BW,the SCS range is from x to y(kHz) and the T_(e_NR) of this SCS range maybe implemented as a same value: N.

Additional Example 5 may include: Maximum Autonomous Time AdjustmentStep (i.e. T_(q_NR)) may be designed differently according to differentSCS. Given a certain downlink BW, if the SCS=x(kHz) and the T_(q_NR) ofthis SCS is N, then the T_(q_NR) of SCS=x/2 (kHz) is 2*N. Given acertain downlink BW, if the SCS=x(kHz) and the T_(q_NR) of this SCS isN, then the T_(q_NR) of SCS=2*x(kHz) is

$\frac{N}{2}.$

Additional Example 6 may include: the Maximum Autonomous Time Adjustment

Step (i.e. T_(q_NR)) may be designed differently according to differentSCS. Given a certain downlink BW, if the SCS=x(kHz) and the T_(q_NR) ofthis SCS is N+L, then the T_(q_NR) of

${SCS} = {\frac{x}{2}({kHz})}$is 2*N+L; L is a fixed margin. Given a certain downlink BW, if theSCS=x(kHz) and the T_(q_NR) of this SCS is N+L, then the T_(q_NR) ofSCS=2*x(kHz) is

${\frac{N}{2} + L};$+L; L is a fixed margin.

Additional Example 7 may include: Maximum Autonomous Time AdjustmentStep (i.e. T_(q_NR)) may be designed differently according to differentSCS. Given a certain downlink BW, if the SCS=x(kHz) and the T_(q_NR) ofthis SCS is N+L, then the T_(q_NR) of

${SCS} = {\frac{x}{2}({kHz})}$is 2*N+2*L; L is an SCS specific margin, e.g.

$L = {\frac{N}{2}.}$Given a certain downlink BW, if the SCS=x(kHz) and the T_(q_NR) of thisSCS is N+L, then the T_(q_NR) of SCS=2*x(kHz) is

${\frac{N}{2} + \frac{L}{2}};$L is an SCS specific margin, e.g.

$L = {\frac{N}{2}.}$

Additional Example 8 may include: Maximum Autonomous Time AdjustmentStep (i.e. T_(q_NR)) may be designed differently according to differentSCS, but same T_(q_NR) may be applied for some of the SCS levels. Givena certain downlink BW, the SCS range is from x to y(kHz) and theT_(q_NR) of this SCS range may be implemented as a same value: N.

Additional Example 9 may include: Timing Error Limit (i.e. T_(e_NR)) maybe designed differently according to different SCS. Given a certaindownlink BW, larger SCS level may have smaller T_(e_NR); smaller SCSlevel may have larger T_(e_NR).

Additional Example 10 may include: the Maximum Autonomous TimeAdjustment Step (i.e. T_(q_NR)) may be designed differently according todifferent SCS. Given a certain downlink BW, larger SCS level may havesmaller T_(q_NR); smaller SCS level may have larger T_(q_NR).

Additional Example 11 may include an apparatus comprising means toperform one or more elements of a method described in or related to anyof Additional Examples 1-10, or any other method or process describedherein.

Additional Example 12 may include one or more non-transitorycomputer-readable media comprising instructions to cause an electronicdevice, upon execution of the instructions by one or more processors ofthe electronic device, to perform one or more elements of a methoddescribed in or related to any of Additional Examples 1-10, or any othermethod or process described herein.

Additional Example 13 may include an apparatus comprising logic,modules, or circuitry to perform one or more elements of a methoddescribed in or related to any of Additional Examples 1-10, or any othermethod or process described herein.

Additional Example 14 may include a method, technique, or process asdescribed in or related to any of Additional Examples 1-10, or portionsor parts thereof.

Additional Example 15 may include an apparatus comprising: one or moreprocessors and one or more computer-readable media comprisinginstructions that, when executed by the one or more processors, causethe one or more processors to perform the method, techniques, or processas described in or related to any of Additional Examples 1-10, orportions thereof.

Additional Example 16 may include a signal as described in or related toany of Additional Examples 1-10, or portions or parts thereof.

Additional Example 17 may include a signal in a wireless network asshown and described herein.

Additional Example 18 may include a method of communicating in awireless network as shown and described herein.

Additional Example 19 may include a system for providing wirelesscommunication as shown and described herein.

Additional Example 20 may include a device for providing wirelesscommunication as shown and described herein.

Embodiments and implementations of the systems and methods describedherein may include various operations, which may be embodied inmachine-executable instructions to be executed by a computer system. Acomputer system may include one or more general-purpose orspecial-purpose computers (or other electronic devices). The computersystem may include hardware components that include specific logic forperforming the operations or may include a combination of hardware,software, and/or firmware.

Computer systems and the computers in a computer system may be connectedvia a network. Suitable networks for configuration and/or use asdescribed herein include one or more local area networks, wide areanetworks, metropolitan area networks, and/or Internet or IP networks,such as the World Wide Web, a private Internet, a secure Internet, avalue-added network, a virtual private network, an extranet, anintranet, or even stand-alone machines which communicate with othermachines by physical transport of media. In particular, a suitablenetwork may be formed from parts or entireties of two or more othernetworks, including networks using disparate hardware and networkcommunication technologies.

One suitable network includes a server and one or more clients; othersuitable networks may contain other combinations of servers, clients,and/or peer-to-peer nodes, and a given computer system may function bothas a client and as a server. Each network includes at least twocomputers or computer systems, such as the server and/or clients. Acomputer system may include a workstation, laptop computer,disconnectable mobile computer, server, mainframe, cluster, so-called“network computer” or “thin client,” tablet, smart phone, personaldigital assistant or other hand-held computing device, “smart” consumerelectronics device or appliance, medical device, or a combinationthereof.

Suitable networks may include communications or networking software,such as the software available from Novell®, Microsoft®, and othervendors, and may operate using TCP/IP, SPX, IPX, and other protocolsover twisted pair, coaxial, or optical fiber cables, telephone lines,radio waves, satellites, microwave relays, modulated AC power lines,physical media transfer, and/or other data transmission “wires” known tothose of skill in the art. The network may encompass smaller networksand/or be connectable to other networks through a gateway or similarmechanism.

Various techniques, or certain aspects or portions thereof, may take theform of program code (i.e., instructions) embodied in tangible media,such as floppy diskettes, CD-ROMs, hard drives, magnetic or opticalcards, solid-state memory devices, a nontransitory computer-readablestorage medium, or any other machine-readable storage medium wherein,when the program code is loaded into and executed by a machine, such asa computer, the machine becomes an apparatus for practicing the varioustechniques. In the case of program code execution on programmablecomputers, the computing device may include a processor, a storagemedium readable by the processor (including volatile and nonvolatilememory and/or storage elements), at least one input device, and at leastone output device. The volatile and nonvolatile memory and/or storageelements may be a RAM, an EPROM, a flash drive, an optical drive, amagnetic hard drive, or other medium for storing electronic data. TheeNB, gNB (or other base station) and UE (or other mobile station) mayalso include a transceiver component, a counter component, a processingcomponent, and/or a clock component or timer component. One or moreprograms that may implement or utilize the various techniques describedherein may use an application programming interface (API), reusablecontrols, and the like. Such programs may be implemented in a high-levelprocedural or an object-oriented programming language to communicatewith a computer system. However, the program(s) may be implemented inassembly or machine language, if desired. In any case, the language maybe a compiled or interpreted language, and combined with hardwareimplementations.

Each computer system includes one or more processors and/or memory;computer systems may also include various input devices and/or outputdevices. The processor may include a general purpose device, such as anIntel®, AMD®, or other “off-the-shelf” microprocessor. The processor mayinclude a special purpose processing device, such as ASIC, SoC, SiP,FPGA, PAL, PLA, FPLA, PLD, or other customized or programmable device.The memory may include static RAM, dynamic RAM, flash memory, one ormore flip-flops, ROM, CD-ROM, DVD, disk, tape, or magnetic, optical, orother computer storage medium. The input device(s) may include akeyboard, mouse, touch screen, light pen, tablet, microphone, sensor, orother hardware with accompanying firmware and/or software. The outputdevice(s) may include a monitor or other display, printer, speech ortext synthesizer, switch, signal line, or other hardware withaccompanying firmware and/or software.

It should be understood that many of the functional units described inthis specification may be implemented as one or more components, whichis a term used to more particularly emphasize their implementationindependence. For example, a component may be implemented as a hardwarecircuit comprising custom very large scale integration (VLSI) circuitsor gate arrays, or off-the-shelf semiconductors such as logic chips,transistors, or other discrete components. A component may also beimplemented in programmable hardware devices such as field programmablegate arrays, programmable array logic, programmable logic devices, orthe like.

Components may also be implemented in software for execution by varioustypes of processors. An identified component of executable code may, forinstance, comprise one or more physical or logical blocks of computerinstructions, which may, for instance, be organized as an object, aprocedure, or a function. Nevertheless, the executables of an identifiedcomponent need not be physically located together, but may comprisedisparate instructions stored in different locations that, when joinedlogically together, comprise the component and achieve the statedpurpose for the component.

Indeed, a component of executable code may be a single instruction, ormany instructions, and may even be distributed over several differentcode segments, among different programs, and across several memorydevices. Similarly, operational data may be identified and illustratedherein within components, and may be embodied in any suitable form andorganized within any suitable type of data structure. The operationaldata may be collected as a single data set, or may be distributed overdifferent locations including over different storage devices, and mayexist, at least partially, merely as electronic signals on a system ornetwork. The components may be passive or active, including agentsoperable to perform desired functions.

Several aspects of the embodiments described will be illustrated assoftware modules or components. As used herein, a software module orcomponent may include any type of computer instruction orcomputer-executable code located within a memory device. A softwaremodule may, for instance, include one or more physical or logical blocksof computer instructions, which may be organized as a routine, program,object, component, data structure, etc., that perform one or more tasksor implement particular data types. It is appreciated that a softwaremodule may be implemented in hardware and/or firmware instead of or inaddition to software. One or more of the functional modules describedherein may be separated into sub-modules and/or combined into a singleor smaller number of modules.

In certain embodiments, a particular software module may includedisparate instructions stored in different locations of a memory device,different memory devices, or different computers, which togetherimplement the described functionality of the module. Indeed, a modulemay include a single instruction or many instructions, and may bedistributed over several different code segments, among differentprograms, and across several memory devices. Some embodiments may bepracticed in a distributed computing environment where tasks areperformed by a remote processing device linked through a communicationsnetwork. In a distributed computing environment, software modules may belocated in local and/or remote memory storage devices. In addition, databeing tied or rendered together in a database record may be resident inthe same memory device, or across several memory devices, and may belinked together in fields of a record in a database across a network.

Reference throughout this specification to “an example” means that aparticular feature, structure, or characteristic described in connectionwith the example is included in at least one embodiment. Thus,appearances of the phrase “in an example” in various places throughoutthis specification are not necessarily all referring to the sameembodiment.

As used herein, a plurality of items, structural elements, compositionalelements, and/or materials may be presented in a common list forconvenience. However, these lists should be construed as though eachmember of the list is individually identified as a separate and uniquemember. Thus, no individual member of such list should be construed as ade facto equivalent of any other member of the same list solely based onits presentation in a common group without indications to the contrary.In addition, various embodiments and examples may be referred to hereinalong with alternatives for the various components thereof. It isunderstood that such embodiments, examples, and alternatives are not tobe construed as de facto equivalents of one another, but are to beconsidered as separate and autonomous representations.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided, such asexamples of materials, frequencies, sizes, lengths, widths, shapes,etc., to provide a thorough understanding of the embodiments. Oneskilled in the relevant art will recognize, however, that theembodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, etc. In otherinstances, well-known structures, materials, or operations are not shownor described in detail to avoid obscuring aspects of embodiments.

It should be recognized that the systems described herein includedescriptions of specific embodiments. These embodiments can be combinedinto single systems, partially combined into other systems, split intomultiple systems or divided or combined in other ways. In addition, itis contemplated that parameters/attributes/aspects/etc. of oneembodiment can be used in another embodiment. Theparameters/attributes/aspects/etc. are merely described in one or moreembodiments for clarity, and it is recognized that theparameters/attributes/aspects/etc. can be combined with or substitutedfor parameters/attributes/etc. of another embodiment unless specificallydisclaimed herein.

Although the foregoing has been described in some detail for purposes ofclarity, it will be apparent that certain changes and modifications maybe made without departing from the principles thereof. It should benoted that there are many alternative ways of implementing both theprocesses and apparatuses described herein. Accordingly, the presentembodiments are to be considered illustrative and not restrictive, andthe description is not to be limited to the details given herein, butmay be modified within the scope and equivalents of the appended claims.

Those having skill in the art will appreciate that many changes may bemade to the details of the above-described embodiments without departingfrom the underlying principles. The scope of the present embodimentsshould, therefore, be determined only by the following claims.

The invention claimed is:
 1. An apparatus for a user equipment (UE), comprising: a wireless interface configured to communicate with a radio access network (RAN) node; and a processor coupled to the wireless interface, the processor configured to: determine a reconfiguration event has occurred, the reconfiguration event corresponding to a first transmission after a random access channel (RACH)-less inter-radio access network (RAN) node handover; and in response to the reconfiguration event: determine a bandwidth (BW) and a subcarrier spacing (SCS); and select a Timing Error Limit (T_(e_NR)) associated with a value N based on the BW, the SCS associated with a value x, and a system basic timing unit.
 2. The apparatus of claim 1, wherein: the T_(e_NR)=N+L when the SCS is x, wherein L is 0 or a fixed margin; the T_(e_NR)≥2·N when the SCS is $\frac{x}{2};$ and the $T_{e\_{NR}} \geq \frac{N}{2}$ when the SCS is 2·x.
 3. The apparatus of claim 1, wherein the $T_{e\_ NR} = {\frac{N}{2} + L}$ when the SCS is 2·x, where L is a fixed margin.
 4. The apparatus of claim 1, wherein the T_(e_NR)=2·N+L when the SCS is $\frac{x}{2},$ where L is a fixed margin.
 5. The apparatus of claim 1, wherein the $T_{e\_ NR} = {\frac{N}{2} + \frac{L}{2}}$ when the SCS is 2 ·x, where L is a fixed margin.
 6. The apparatus of claim 1, wherein the T_(e_NR)=2·N+2·L when the SCS is $\frac{x}{2},$ where L is a fixed margin.
 7. The apparatus of claim 1, wherein the processor is a baseband processor.
 8. A user equipment (UE) for determining a Maximum Autonomous Time Adjustment Step (T_(q_NR)), the UE comprising: storage for the T_(q_NR); and a processor configured to: determine a reconfiguration event has occurred, the reconfiguration event corresponding to a first transmission after a random access channel (RACH)-less handover inter-radio access network (RAN) node; and in response to the reconfiguration event: determine a bandwidth (BW) and a subcarrier spacing (SCS); and select the T_(q_NR) associated with a value N based on the BW, the SCS associated with a value x, and a system basic timing unit.
 9. The UE of claim 8, wherein: the T_(q_NR)=N+L when the SCS is x, wherein L is 0 or a fixed margin; the T_(q_NR)≥2·N when the SCS is $\frac{x}{2};$ and the $T_{q\_{NR}} \geq \frac{N}{2}$ when the SCS is 2·x.
 10. The UE of claim 8, wherein the $T_{q\_ NR} \geq {\frac{N}{2} + L}$ when the SCS is 2·x, where L is a fixed margin.
 11. The UE of claim 8, wherein the T_(q_NR)=2·N+L when the SCS is $\frac{x}{2},$ where L is a fixed margin.
 12. The UE of claim 8, wherein the $T_{q\_ NR} = {\frac{N}{2} + \frac{L}{2}}$ when the SCS is 2·x, where L is a fixed margin.
 13. The UE of claim 8, wherein the T_(q_NR)=2·N+2·L when the SCS is $\frac{x}{2},$ where L is a fixed margin.
 14. The UE of claim 8, wherein the processor is a baseband processor.
 15. A computer program product comprising a non-transitory computer-readable storage medium that stores instructions for execution by a processor to perform operations of a user equipment (UE), the operations, when executed by the processor, to perform a method, the method comprising: determining a reconfiguration event has occurred, the reconfiguration event corresponding to a first transmission after a random access channel (RACH)-less inter-radio access network (RAN) node handover; and in response to the reconfiguration event: determining a bandwidth (BW) and a subcarrier spacing (SCS); and selecting a Timing Error Limit (T_(e_NR)) based on the BW associated with a value N, the SCS associated with a value x, and a system basic timing unit T_(S_NR).
 16. The computer program product of claim 15, wherein selecting the comprises selecting the T_(e_NR) from a table based on the BW and the SCS being between two values or equal to one of the two values.
 17. The computer program product of claim 15, wherein the $T_{e\_ NR} = {\left( {\frac{N}{2} + L} \right) \cdot T_{S\_ NR}}$ when the SCS is 2·x, and where L is a fixed margin.
 18. The computer program product of claim 15, wherein the $T_{e\_ NR} = {\left( {\frac{N}{2} + \frac{L}{2}} \right) \cdot T_{S\_ NR}}$ when the SCS is 2·x, and where L is a fixed margin. 